-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: github actions to build browser extension for pull requests #373
Conversation
chore: test action
chore: test action
* testing PR * test * test * test * test * test * test * test * test * test
* testing PR * test * test * test * test * test * test * test * test * test * test
No worries about the multiple commits. Unfortunately there's no other way to test github actions, so this was expected :) i'll squash them into one commit so not a problem. Lets see if we can combine the two actions into 1. I think we could build the firefox and chrome version in the same action. So the build action could look something like
Then configure the upload-artifact action :
I think this would create one artifact zip files with two folders for each extension. |
I think the github actions are failing because we haven't given write access for |
Builds the extension for firefox and chrome and adds a link to them under the PR comments section.
Describe the PR
This PR resolves #347.
This PR has the github action code to build the browser extension when a pull request is made to the
main
branch oftattle-made/Uli
.Once a user makes the PR, a comment (bot) will pop up having 2 links. One which contains the build folder for firefox and the other for chrome.
Steps to test the PR
main
branch oftattle-made/Uli
@dennyabrain apologies for the large number of commits, but every time to test a change in the action, I had to push the changes and make a PR to test them out.